@venky225 can you look into why vitest upgrade causes the tests to fail?

@julesyan
Test cases are failing with following reason.
Vitest cannot be imported in a CommonJS module using require()" because vitest scans and attempts to run compiled test files in dist/vitest/*.test.js (CommonJS format), in addition to the source TypeScript files.

Root Cause:

1. TypeScript is configured to compile to CommonJS ("module": "commonjs" in vscodeclle\language\tsconfig.jsontsconfig.json)
2. Test files in vitest/ get compiled to CommonJS in dist/vitest/
3. Vitest attempts to load both the .ts source files AND the .js compiled files

There are couple of solutions which I tried and they are working fine.

1. Created vitest.config.ts that explicitly tells vitest to run only .ts files.
   include: ['vitest/**/*.test.ts']
2. Changing the module to esnext ( "module": "esnext",) from commonjs in tsconfig.json (Test cases will run twice here. 1 for Source and 1 for compiled)

Please use the first solution as that is consistent with the vscode-ibmi repository

Please use the first solution as that is consistent with the vscode-ibmi repository

@julesyan
Updated the vitest. Now we are left with 3 vulnerabilities which are occurring from mocha. We need to wait for mocha to update their dependencies.

Are we using mocha in the project. I don't see it being used anywhere. Can we uninstall mocha.?

Yes we can remove mocha from the dependancies

Yes we can remove mocha from the dependancies

Done. All vulnerabilities have been resolved. Please verify.

@venky225 I went ahead and pushed some additional changes to make the extension compatible with Code4i 3.0.0. Also, I bumped a few more packages.